Except for the two buttons on this stack labeled ΓÇ£Delete FilesΓÇ£ and ΓÇ£Append FilesΓÇ¥, no Free Text operations should *ever* change the contents of any of your database files. Let me know at once of any apparent exceptions, please!
If you get a beep and a warning of a non-fatal error, you can probably continue working ΓÇö but think first. Did you try to use an advanced feature without reading the instructions above? (That's OK, as long as you don't make a mistake!) Did you attempt to open a database file which hasn't been indexed, or which has been changed since indexing last took place? Did you try to build an index to a file which already had old key and pointer files on disk? (You will find some new index files with temporary names such as ΓÇ£z3k0ΓÇ¥ and ΓÇ£z3p0ΓÇ¥; if you like, instead of re-indexing just throw away the old .k and .p files and rename the new ones appropriately.) Did you scroll or jump off one end of the database?
Were you pushing the envelope in some other direction? Free Text attempts to catch any errors you may make, but I would greatly appreciate being notified of any other ΓÇ£safety netsΓÇ¥ which I should incorporate in the next version of the system.
